Your site preview for commit 98ce830 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17431-98ce8300.s3-website.us-west-2.amazonaws.com.

@claude review this PR and make some changes. 1/ Remove the NPW screenshots as they are outdated, 2/ include a link to the no code docs: https://www.pulumi.com/docs/idp/get-started/workflows 3/ the note: section is not used for doc structure.

Claude finished @meagancojocar's task in 1m 27s —— View job

Changes completed ✓

Tasks

• Read the modified file to understand current state
• Remove outdated NPW screenshots
• Add link to no-code docs (https://www.pulumi.com/docs/idp/get-started/workflows)
• Fix the "note:" section formatting
• Commit and push changes

Summary

I've made all the requested changes to the New Project Wizard documentation:

1. Removed outdated screenshots: Deleted 3 screenshot files (npw-sidebar.png, npw-start.png, npw-deploy-method.png) and their references in the markdown file

2. Updated no-code link: Changed the link from /docs/idp/get-started/workflows/#no-code to /docs/idp/get-started/workflows as requested

3. Fixed documentation structure: Removed the {{% notes %}} shortcode wrapper and converted it to regular paragraph content, which better fits the document structure

The changes have been committed and pushed to the PR branch claude/slack-fix-project-wizard-docs-bBFUQ.

Branch |

@claude new project is now a button on the "Stacks" page found on the left nav, url is https://app.pulumi.com/pulumi/projects. and the URL for going direct to new project is https://app.pulumi.com/new

Claude finished @meagancojocar's task in 1m 18s —— View job

Changes completed ✓

Tasks

• Read current documentation file
• Update navigation information with new URLs
• Commit and push changes

Summary

I've updated the New Project Wizard documentation to include information about how to access the feature:

Changes made:

1. Added new section: "Accessing the New Project Wizard" that explains:

   • The New Project button is located on the Stacks page in the left navigation
   • Direct link to the Stacks page: https://app.pulumi.com/pulumi/projects
   • Direct link to the wizard: https://app.pulumi.com/new

2. Improved document structure: Promoted the deployment method subsections from h4 to h3 headers for better hierarchy and readability

The changes have been committed and pushed to the PR branch claude/slack-fix-project-wizard-docs-bBFUQ.

Note: I was unable to run make lint due to permission restrictions. You may want to verify the linting passes in the CI pipeline.

--- | Branch

Your site preview for commit 24e678b is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17431-24e678bd.s3-website.us-west-2.amazonaws.com.

Your site preview for commit 49c060f is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17431-49c060fb.s3-website.us-west-2.amazonaws.com.

@claude the new project button is not in the left nav anymore, its on the stacks page. dont link to the projects page as that url has so won't work for anyone but pulumi

Claude finished @meagancojocar's task in 47s —— View job

Tasks

• Read current documentation file
• Update navigation instructions to remove left nav reference
• Remove link to projects page with org-name
• Update accessing section with correct information
• Commit and push changes

Summary

I've updated the New Project Wizard documentation to fix the navigation instructions:

Changes made:

1. Removed left navigation reference: The section no longer mentions "Look for the 'New Project' button in the left navigation"
2. Removed projects page link: Deleted the link to https://app.pulumi.com/pulumi/projects which contained the org-name placeholder
3. Simplified instructions: The accessing section now simply states that users can click the "New Project" button on the Stacks page, or navigate directly to the wizard URL

The updated text now reads:

"You can access the New Project Wizard by clicking the 'New Project' button on the Stacks page in the Pulumi Cloud console. You can also navigate directly to the wizard at https://app.pulumi.com/new."

The changes have been committed and pushed to the PR branch claude/slack-fix-project-wizard-docs-bBFUQ.

View job | Branch

Your site preview for commit 398a203 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17431-398a203d.s3-website.us-west-2.amazonaws.com.

Documentation Review

I've reviewed the changes to document deployment method options in the New Project Wizard. Here are my findings:

Issues Found

1. Inconsistent terminology (line 61)

The heading uses "Pulumi Deployments" but should use "Deployments - git" to match the deployment method terminology used at line 22.

content/docs/idp/developer-portals/new-project-wizard/_index.md:61

1. Choose "Deployments - git" as the deployment method

2. Inconsistent deployment method naming (line 44)

The text says "Choose 'Deployments - no-code'" but this should match the exact terminology used in the heading and bullet list at lines 21-23. All three deployment methods should use consistent naming throughout.

content/docs/idp/developer-portals/new-project-wizard/_index.md:44

1. Choose "Deployments - no-code" as the deployment method

3. Unbalanced list formatting

The three deployment method sections have inconsistent list numbering and structure. The "Deployments - no-code" section (lines 42-45) and "Deployments - git" sections (lines 59-62) use numbered lists starting with "1.", while the CLI section (lines 71-74) doesn't follow the same structure. For consistency, all three "How it works" sections should use the same list format.

content/docs/idp/developer-portals/new-project-wizard/_index.md:71-74

1. Select a template and provide configuration values
1. Copy the generated CLI commands
1. Run the commands locally to create and deploy your project

Positive aspects

• Clear section structure with deployment methods well-organized
• Good use of requirements sections for each deployment method
• Helpful cross-references to related documentation
• Removal of outdated images is appropriate given the updated content structure
• Content accurately describes the three deployment options

Style compliance

• Headings follow proper capitalization (H2+ sentence case)
• Links are properly formatted with descriptive text
• No spelling or grammar issues detected
• Proper use of Markdown formatting

If you'd like me to review additional changes or help fix these issues, mention me (@claude) in a comment.

Your site preview for commit 398a203 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-17431-398a203d.s3-website.us-west-2.amazonaws.com.